Just moved to v9.6.3.1. My "addins" is now hosed up. Can someone point me to documentation? We moved 9.5/config to 9.6/config in the registry. We have an installed "addins" variable in HKLM in registry. I've overwridden that with "addins" in HKCU. Now even when I delete the HKCU "addins" variable, I get no "addins" at all; getenv("addins") and getenv("DOORSADDINS") return nothing. There are no command line switches. When I add "addins" with "xx" it sees that. I cannot go back to the original HKLM version. I've searched the registry. This seems to be on my client PC; Citrix seems to be working correctly in this regard. -Louie For whatever it is worth, I notice Citrix has removed the "Wow6432Node" path from the HKLM path to doors config. llandale - Tue Sep 15 10:22:09 EDT 2015 |
Re: v96 Addin Woes v9.6 onwards, DOORS is 64-bit. So HKLM path will vary, as compared to 9.5. As you noticed on Citrix, it won't be under Wow6432Node, but directly under Software (HKEY_LOCAL_MACHINE\SOFTWARE\Telelogic\DOORS\9.6\Config). So I'd suggest you to ensure it is in the correct HKLM path. But that doesn't explain why DOORS would see a dummy value.. there could be something else still. |
Re: v96 Addin Woes SudarshanRao - Tue Sep 15 10:34:55 EDT 2015 v9.6 onwards, DOORS is 64-bit. So HKLM path will vary, as compared to 9.5. As you noticed on Citrix, it won't be under Wow6432Node, but directly under Software (HKEY_LOCAL_MACHINE\SOFTWARE\Telelogic\DOORS\9.6\Config). So I'd suggest you to ensure it is in the correct HKLM path. But that doesn't explain why DOORS would see a dummy value.. there could be something else still. Solved. The companies v96 installer failed to notice the change in location in the registry. So while I looked at the hkLM "wow" area and there was indeed an "addins" variable, DOORS doesn't use that area anymore. The new area has no "addins" variable. -Louie So I proudly wrote up the error in the install script and sent it to them; just to be rebuffed that the new installer is coming out tomorrow. |